Document Bits Code organization env vars - #39722
Open
Vyncentddog wants to merge 1 commit into
Open
Conversation
Contributor
|
I can only run on private repositories. |
Contributor
Preview links (active after the
|
joepeeples
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Documents organization-level environment variables and secrets for Bits Code repository environments, so users know they can define values once for the whole organization instead of repeating them per repository. Also documents how repository environments override or opt out of inherited values, and that testing a setup command requires write access to the selected repository.
Source PRs:
Changes in
hugo/content/en/bits_ai/bits_code/setup.md, under Environment setup > Configure repository environment:Configure organization environment variables and secretssubsection covering inheritance, availability during setup versus Bits Code execution, opt-out and restore behavior, naming requirements, behavior when a repository has no setup command, and the permissions required to manage the configuration.Testing
Reviewed the rendered Markdown structure, heading level, anchor link target, and reference-style link IDs for consistency with the rest of the page.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Drafted with Bits Code, then reviewed for style and consistency with the existing page.
Additional notes
PR by Bits - View session in Datadog
Comment @DataDog to request changes